Enabling electronic documents for limited-capability computing devices

ABSTRACT

System(s), method(s), and/or techniques (“tools”) are described that enable electronic document functionality for a limited-capability computing device. The tools may enable a computing device with limited display capabilities to present and enable navigation through nested items or hierarchical view levels of an electronic document. The tools may also build renderable view information by which a device may enable electronic document functionality based on the capabilities of that device.

BACKGROUND

Currently, many users interact with network-enabled electronic documents, like web pages and electronic forms. They may do so through a computing device having extensive capabilities, like a desktop or laptop computer having a large screen, large memory capacity, and a fast processor. More and more, however, users want to interact with these documents through computing devices with more-limited capabilities, such as hand-held personal digital assistants (PDAs) and cellular phones.

SUMMARY

System(s), method(s), and/or techniques (“tools”) are described that enable electronic document functionality for a limited-capability computing device. The tools may enable a computing device with limited display capabilities to present and enable navigation through nested items or hierarchical view levels of an electronic document. The tools may also build renderable view information by which a device may enable electronic document functionality based on the capabilities of that device.

In some cases the tools enable these and other techniques using an intermediary between a limited-capability computing device and a network computing architecture, where the network computing architecture is capable of enabling an electronic document's functionality on a high-capacity computing device but not on the limited-capacity computing device. This intermediary may enable the electronic document's functionality on the limited-capability computing device without requiring alteration to the electronic document or the network computing architecture.

This Summary is provided to introduce a selection of concepts in a simplified form that are further described below in the Detailed Description. This Summary is not intended to identify key or essential features of the claimed subject matter, nor is it intended to be used as an aid in determining the scope of the claimed subject matter.

BRIEF DESCRIPTION OF THE DRAWINGS

FIG. 1 illustrates an exemplary operating environment in which various embodiments can operate.

FIG. 2 illustrates an exemplary, editable electronic document displayed on a high-capability device.

FIG. 3 illustrates exemplary hierarchical view information for the editable electronic document shown in FIG. 2.

FIG. 4 is an exemplary process describing manners in which the tools enable electronic document functionality.

FIG. 5 illustrates an exemplary rendering of the exemplary editable electronic document shown in FIG. 2 but displayed instead on a limited device and showing one hierarchical view level.

FIG. 6 illustrates an exemplary rendering of the exemplary editable electronic document shown in FIGS. 2 and 5 but displaying nested items of a second hierarchical view.

FIG. 7 illustrates the rendering of FIG. 6 following an edit.

FIG. 8 illustrates the exemplary, editable electronic document of FIG. 2 displayed on a high-capability device following an edit to the electronic document on a limited device.

The same numbers are used throughout the disclosure and figures to reference like components and features.

DETAILED DESCRIPTION

Overview

The following document describes tools capable of many powerful techniques, including enabling electronic document functionality in a limited-capability computing device. In some cases the tools enable these techniques with an intermediary acting between the limited-capability computing device and a network computing architecture. This intermediary may permit an existing network computing architecture and electronic document to be used, in some cases without alteration, to enable electronic document functionality in a device that the network computing architecture is otherwise incapable of enabling.

An environment in which the tools may enable these and other techniques is set forth first below in a section entitled Exemplary Operating Environment. This section is followed by another section describing processes for enabling these and other techniques, entitled Enabling Functionality for Limited Devices.

Exemplary Operating Environment

Before describing the tools in detail, the following discussion of an exemplary operating environment is provided to assist the reader in understanding some ways in which various inventive aspects of the tools may be employed. The environment described below constitutes but one example and is not intended to limit application of the tools to any one particular operating environment. Other environments may be used without departing from the spirit and scope of the claimed subject matter.

FIG. 1 illustrates one such operating environment generally at 100 having a high-capability computing device 102 (“high-capability device”), a limited-capability computing device 104 (“limited device”), a communication network 106, and a network computer 108.

The high-capability device has at least one high capability related to electronic documents, such as a display capable of presenting two or more hierarchical view levels and/or nested items (both described later below) or processor(s) and/or memory enabling view information to be built for a browser, such as by storing and executing software capable of building view information.

Here the high-capability device is shown having one or more processor(s) 110, computer-readable media 112, and a display 114. The processors are capable of accessing and/or executing the computer-readable media. The computer-readable media comprises or has access to a browser 116, which is a module, program, or other entity capable of interacting with a network-accessible entity (e.g., network computer 108), and local view-information builder 118. The browser is capable of rendering on the display renderable view information, such as information expressed using a markup-language (e.g., HTML: HyperText Markup Language or WML: Wireless Markup Language). The local view-information builder is capable of building renderable view information from non-renderable view information. In some cases the builder does so using hierarchical view information and renderable pieces of view information associable with the hierarchical view information.

Limited device 104 has at least one limited capability related to electronic documents, such as having a display incapable of presenting (in an appropriate size and readability to a user) two or more hierarchical view levels and/or nested items, or lacking the processor capabilities, memory, and/or installed modules or programs that would be required in order to allow view information to be built on the limited device. The limited device may be a small computing device, such as a handheld personal digital assistant or a cellular phone.

Here the limited device is shown having a processor 120, computer-readable media 122, and a display 124. The processors are capable of accessing and/or executing the computer-readable media. The computer-readable media comprise or have access to a browser 126, which is a module, program, or other entity capable of interacting with a network-accessible entity (e.g., network computer 108). The browser 126 is capable of rendering on the display 124 renderable view information and enabling interaction with an electronic document through that rendering, such as through a tablet screen or letter/number pad. The renderable view information may be information expressed using a markup-language (e.g., HTML or WML) or some other renderable format.

The operating environment's network 106 enables communication between the devices 102 and/or 104 and the network computer 108. The network may be a global or local, wired or wireless network, such as the Internet or a company's intranet.

Network computer 108 is shown having or having access to processor(s) 128, computer-readable media 130, and intermediary 132. The intermediary is shown with the network computer and may be part of the network computer's computer-readable media, though it may also be separate, such as on another network-accessible entity (e.g., another network computer).

The network computer's processor(s) are capable of accessing and/or executing computer-readable media 130. This computer-readable media comprises or has access to an electronic document 134 and a network computing architecture 136. The electronic document may be editable (such as an electronic form having data-entry fields) or uneditable (such as a webpage into which data entry or other edits cannot be made). It may also have two or more hierarchical viewing levels or levels of nested items.

In FIG. 2, for example, an exemplary, editable electronic document 134 is displayed on the high-capability device's display 114. The electronic document is shown having some top-level information (Person, Purpose, Contributor) together with a list of four people (or groups of people), 202, 204, 206, and 208, along with information about each of them, here their names 210, 212, 214, and 216, and their roles 218, 220, 222, and 224, both respectively. This information is displayed in data-entry fields through which a user may edit this information.

This rendering of the electronic document shows multiple levels of hierarchy on the display at once. There is the top-level information, and the first level of hierarchical information, here the people (or groups of people). Then there is the second level of hierarchical information—here the information about these people (their names and roles). The items of information in this second level are nested in relation to the first level.

Electronic document 134 comprises or has access to hierarchical view information 138 and, if the electronic document is editable, data instance 140. The hierarchical view information may comprise or represent many hierarchical view levels and nested items. For example, if an electronic document associated with the hierarchical view information about a company has vice presidents with managers and the managers have employees that they manage, the hierarchical view information may represent, in addition to the top-level information about the company, three hierarchical view levels—one level for all of the vice presidents, one for all of the managers, and one for all of the employees. Each hierarchical view level may have additional nested items. The additional nested items may contain further information related to the particular level in the hierarchy, such as nested items for each of the vice presents, each of the managers, or each of the employees. Nested items for each of the vice presidents may include information about that vice president, nested items for each of the managers may include information about the manager, and so forth.

In FIG. 3, exemplary hierarchical view information 138 is illustrated for the electronic document shown in FIG. 2. This hierarchical view information has the top-level Root Node, with a first hierarchical view level 302, and a second hierarchical view level 304. The nested items 306, 308, 310, 312, 314, 316, 318, and 320 are at the second hierarchical view level 304. Nested items 306 and 308 are related and provide information about people node 322 for the person named “Robert Jenkins,” shown in FIG. 2. Nested items 310 and 312 are related and provide information about people node 324 for the person named “Pete Jenkinson.” Nested items 314 and 316 are related and provide information about people node 326 for the group of people named “Henrietta Hastings and her extended family.” Nested items 318 and 320 are related and provide information about people node 328 for the person named “Jennifer Jones.”

Each nested item or set of nested items may also have a subordinate nested item and this subordinate nested item its own further subordinate nested item (not shown). For the exemplary hierarchical view information of FIG. 3, a subordinate nested item could comprise items of information about a person's role, for instance.

Returning to FIG. 1, network computing architecture 136 is capable of enabling electronic document functionality for the high-capability device. In some cases the network computer does so through a smart rendering architecture (e.g., AJAX) with script and XMLHTTP (extensible Markup Language (XML) HyperText Transfer Protocol (HTTP)).

This functionality may include display of all or multiples of the electronic document's hierarchical levels or nested items for the electronic document, and enabling and storing edits to the electronic document (e.g., in a data instance for an editable electronic document), and executing business logic (i.e. special code or complex behavior) incorporated into, or associated with, the electronic document. The network computing architecture may not be able, on the other hand, to enable all of these electronic document's functionalities for the limited device.

Intermediary 132 acts between the limited device and the network computing architecture to enable electronic document functionality in the limited device. The intermediary may, for example, enable (in conjunction with the network architecture) each hierarchical level and every nested item to be displayed and interacted with through a limited device. It may do so even if that limited device does not have a display capable of presenting at one time multiple hierarchical levels or nested items that the high-capability device might otherwise present at once.

The intermediary may also enable functionality for a same electronic document to which the network computing architecture enables functionality for a high-capability device. The intermediary may enable this functionality without altering the electronic document or its business logic, the network architecture, and/or a data instance of the electronic document. By so doing, the intermediary may allow a user to edit a data instance of an electronic document with a high-capability device and maintain these edits for continued editing of the same data instance with a limited device and vice-a-versa. By enabling functionality without altering the network computing architecture, the intermediary permits an existing network architecture capable of enabling functions of a high-capability device to be used to enable the same or similar functionality for a limited device.

The intermediary has renderable pieces 142 by which it may build renderable view information 144. With this renderable view information, a limited device's browser may render and enable functions of an electronic document. Ways in which the intermediary may build this renderable view information are described in greater detail below.

Enabling Functionality for Limited Devices

The following discussion describes exemplary ways in which the tools enable electronic document functionality for a limited device and other inventive techniques. The tools permit a single electronic document or its data instance to be used to enable functionality for that electronic document with both limited and high-capability devices. This interoperability permits a programmer to build a single electronic document and have that electronic document usable by users of both high-capability and limited devices. This interoperability also permits users to interact with the same data instance of an electronic document with a limited device and a high-capability device.

FIG. 4 is an exemplary process 400 enabling electronic document functionality. It is illustrated as a series of blocks representing individual operations or acts performed by elements of operating environment 100 of FIG. 1, such as intermediary 132 and network computing architecture 136. This process may be implemented in any suitable hardware, software, firmware, or combination thereof; in the case of software and firmware, this process represents a set of operations implemented as computer-executable instructions stored in computer-readable media and executable by one or more processors.

Block 402 receives a request to treat a device as limited or receives capabilities of the device, such as the size of the device's display or memory, its processor speed, and/or its local software capabilities. Continuing the embodiment described above, assume that the device's capabilities correspond to the high-capability device 102 or the limited device 104.

If no request to treat the device as limited is received, block 402 proceeds along the “Do Not Treat as Limited” path to block 404. If the device is requested to be treated as limited, block 402 proceeds to block 406 along the “Treat as Limited” path.

Block 404 determines whether the device has limited capabilities and proceeds to blocks 406 or 408. If the device has limited capabilities, such as limited device 104 of FIG. 1, it proceeds to block 406 along the “Yes” path. If not, it proceeds along the “No” path to block 406.

Block 404 may determine this based in part on a particular electronic document being requested or the network computing architecture for which intermediary 132 is interceding. Thus, if the network computing architecture is capable, without assistance from the intermediary, of enabling a particular electronic document's functionality for a particular device, the intermediary may make this determination and refrain from continuing to intercede. If a device has a limited processor, but the network computing architecture is still capable of enabling a requested electronic document's functionality without aid from the intermediary, the tools may proceed along the “No” path even though the device has some limitations. In so doing, block 404 may determine whether or not the device's capabilities are too limited for the network computing architecture to enable a requested electronic document's functionality without assistance.

Here we assume first that block 404 determines that the device does not have limited capabilities (e.g., the request is from high-capability device 102) and so proceeds to block 406.

Block 408 enables functionality for the requested electronic document. Here the network computing architecture enables the high-capability device to edit, display, and otherwise use electronic document 134. In some cases the network computing architecture does so by creating renderable view information (similar or dissimilar to renderable view information 144) for the high-capability device to render (e.g., HTML or WML).

In another case, the network computing architecture sends the hierarchical view information 138 and renderable pieces 142 for the electronic document to the high-capability device (renderable pieces 142 are shown in intermediary 132 but may also be stored or accessible by the network computing architecture). The high-capability device may then build renderable view information using local view-information builder 118. This view information may then be rendered by browser 116, here as shown in FIG. 2. In this case edits to an electronic document may be reflected (though not actually made to the electronic document's data instance) without a postback to the network computer. The local view-information builder may render edits as if they were made to the electronic document's data instance. The edits may be retained by the high-capability device in an event log, which may later be submitted to the network computer. The network computing architecture may then receive the edits in the event log and make the appropriate changes to the data instance for that electronic document.

If block 404 determines that the device's capabilities are limited, however, it proceeds to block 406 rather than block 408. Block 406 receives hierarchical view information associated with an electronic document and having hierarchical viewing levels and/or nested items. The hierarchical view information may be a set of relationships derived from a data model for an electronic document, such as a name-value-pair table of records or a hierarchical data model. The hierarchical view information indicates relationships between portions of an electronic document, such as a manager having nested information about the manager and employees for which the manager is responsible.

In this particular case intermediary 132 receives the exemplary hierarchical View information 138 shown in FIG. 3.

Block 410 builds renderable view information enabling a limited device to enable an electronic document's functionality. Block 410 may do so without user interaction in cases where a user does not specifically select to treat the device as limited.

This renderable view information may permit a device having limited capabilities to enable a user to interact with the electronic document sufficient to allow use of the electronic document's functionality. One such case is where the viewing capabilities of the device do not permit viewing multiple hierarchical view levels. In this case block 410 may build the renderable view information to present just those levels viewable on the limited capability display.

While the electronic document may appear different visually, the functionality permitted by the network computing architecture in conjunction with the intermediary and limited device may be identical to that enabled by the network computing architecture and the high-capability device without the intermediary.

Here block 410 builds renderable view information enabling the limited device to present a first hierarchical view level and indicia by which a user may select to proceed to another hierarchical view level (or nested items of the first hierarchical view level). In so doing, the intermediary may switch between a smart rendering architecture used by the network computing architecture and XMLHTTP and a simpler HTML (or WML) based renderable view information enabling the limited device to present hierarchical view levels and otherwise enable the electronic document's functionality. To use the simpler HTML-based renderable view information, the limited device may communicate interactions with the electronic document to the intermediary using full-page postback.

FIG. 5 sets forth an exemplary rendering 500 of the same exemplary electronic document shown in FIG. 2, though here displayed with limited device 104 and showing the top-level content (here, Person and Purpose), along with just one hierarchical view level 502 rather than two. The hierarchical view level 502 corresponds to the first hierarchical level 302 of FIG. 3, that of four people, 202, 204, 206, and 208. Note that the size of this display is incapable of presenting at once nested items from a second hierarchical view level (in this example, Role—or any other nested items from that level of the hierarchy) along with items from the first hierarchical view level. Nor could other items from deeper levels of hierarchy be shown at the same time (such as additional information about each Role).

The intermediary may enable the limited device to show this hierarchical level with information about the items in this level. The intermediary, when building the renderable view information, may extract textual information about items in one level (here the people), by retrieving just the first textual, nested item at the next level (here the name). Here the intermediary extracts the people's names 210, 212, 214, and 216 from nodes 306, 310, 314, and 316 of FIG. 3, respectively.

The intermediary also permits the limited device to navigate through the electronic document. This enables the user to interact with the functions and information of the electronic document even when the user may not be able to see or interact with all of these functions at one time.

Here the intermediary adds selectable indicia 504, 506, 508, and 510 to the renderable view information by which a user may navigate through hierarchical view levels and nested items. The selectable indicia may be geographically associated with information, be the information itself, or otherwise indicate the item and enable selection. Here a user selects to view and interact with the nested items of the group of people associated with indicia 508.

Block 412 receives a selection to navigate to another hierarchical view level and/or nested items. The selection may be to a higher or lower hierarchical view level or nested items, such as to multiple levels of subordinate nested items.

Block 414 builds another renderable view information responsive to the user's selection to navigate. Here the intermediary builds renderable view information to present the nested items, here “name” and “role” associated with “Henrietta Hastings and her extended family.”

FIG. 6 sets forth an exemplary rendering 600 of the same exemplary electronic document shown in FIGS. 2 and 5, though here displaying nested items of a second hierarchical view that are associated with the selected indicia. Rendering 600 shows information 602 and 604 from nested items 314 (“name”) and 316 (“role”) that are related to people 326 of FIG. 3. Information from these same nested items are also shown in FIG. 2 at 214 and 222.

Each of these two renderable view information may also enable a user to edit the electronic document's data, assuming it is an editable electronic form. In rendering 600, for instance, a user may edit the group's name or role.

FIG. 7 shows an edit to Henrietta's role, here changing it from “author” to “screenwriter” at 702. The limited device (or high-capability device if selected to be treated as a limited device) may submit this to the intermediary, such as when a user tabs out of the field or presses a submit or save button.

Block 416 receives an edit to an electronic document. The edit may be to change something in an item or nested item, add items, or perform operations (e.g., business logic operations such as zip-code correction or tax calculations). Here the intermediary receives an edit to change the contents of nested item 316 of FIG. 3. The intermediary may receive the edit as a postback name-value pair or otherwise.

Block 418 translates the edit. The edit may or may not be in a form understandable by the network computing architecture. Here the edit is received by the intermediary as a postback name-value pair. The network computing architecture is built to receive and handle edits in the form of an event log. So here the intermediary translates this postback into an event log. The network computing architecture receives the event log, alters the data instance to reflect the edit in the event log, and sends the altered data instance to the intermediary. This is one way in which the same data instance of an electronic document may be edited by a limited device and a high-capability device. Here the data instance is altered to reflect the edit from “author” to “screenwriter” as if the edit were made to a high-capability device handled directly by the network computing architecture.

Block 420 receives results based on the edit. Here the intermediary receives the edited data instance from the network computing architecture.

Block 422 builds renderable view information responsive to the altered data instance. Here again the intermediary builds renderable view information based on the hierarchical view information and the renderable pieces. When there is a data instance (as in the ongoing example), it is also used to build the renderable view.

With the altered data instance, the intermediary builds renderable view information capable of being rendered by the limited device and showing the results of the edit. Here that result is simply changing the role from author to screenwriter. In some cases, however, the result of an edit may cause a substantial change to the data instance and the hierarchical view information. If the edit caused many data-entry fields to be altered or added, the intermediary may still build renderable view information to reflect and enable functionality associated with this change.

The tools may enable edits to an electronic document made with a high-capability device or limited device to be interchangeable. As described above, a user can make an edit to an electronic document with either device and have that edit reflected in the electronic document's data instance. Thus, if the user later returns to the electronic document using a different device, he or she may continue to edit the electronic document's data instance. An example of this interoperability is shown in FIG. 8.

FIG. 8 sets forth a rendering 800 displayed on the high-capability device showing the results of the user's edit made through the limited device. The edit to Henrietta's role is shown at 802.

Blocks 412 and 414 may be repeated, as may blocks 416, 418, 420, and 422. Thus, a user may continue to navigate back and forth through hierarchical view levels and many levels of nested items to view and interact with functionality of an electronic document. The user may also make many edits to an electronic document and see the results of these edits.

CONCLUSION

The above-described systems and methods enable electronic document functionality for a limited-capability computing device. These systems and methods may do so using an existing network computing architecture and electronic document that otherwise may not be able to permit this functionality through a limited-capability computing device. By so doing, these systems and methods permit interoperability between high-capability computing devices and limited-capability computing devices. They also permit existing electronic documents and network computing architecture to be reused, thereby potentially saving extensive programming and computing resources. Although the systems and methods have been described in language specific to structural features and/or methodological acts, it is to be understood that the systems and methods defined in the appended claims are not necessarily limited to the specific features or acts described. Rather, the specific features and acts are disclosed as exemplary forms of implementing the claimed systems and methods. 

1. One or more computer-readable media residing on a computer and having computer-readable instructions therein that, when executed by the computer, cause the computer to: act as an intermediary between a limited-capability computing device and a network computing architecture, the network computing architecture being capable of enabling an editable electronic document functionality on a high-capability computing device but not on the limited-capability computing device, the computer being remote from the high-capability computing device and the limited-capability computing device; determine, based on the editable electronic document functionality and viewing capabilities of the limited-capability computing device, that the network computing architecture is incapable of enabling the editable electronic document functionality on the limited-capability computing device without external assistance, the editable electronic document functionality including at least some view information associated with an editable electronic document that is requested by the limited-capability computing device from the network computing architecture; enable the limited-capability computing device to perform the editable electronic document functionality; and edit an instance of the editable electronic document that is associated with the editable electronic document functionality and that is stored on the computer but not on the limited-capability computing device, wherein editing the instance of the editable electronic document includes executing one or more business logic operations via the instance of the editable electronic document and responsive to input to the limited-capability computing device, the editing comprising: receiving, from the limited-capability computing device, a postback that comprises a name-value pair; translating the postback into an event log; and editing the instance of the editable electronic document based on the event log.
 2. The media of claim 1, wherein the editable electronic document functionality comprises interacting with nested items of the editable electronic document.
 3. The media of claim 1, wherein the editable electronic document functionality is enabled by business logic associated with the editable electronic document, and wherein the instructions are capable, when executed and in conjunction with network computing architecture, of enabling the business logic on both the limited-capability computing device and the high-capability computing device without altering the business logic.
 4. The media of claim 1, wherein the instructions, when executed, are further capable of enabling the network computing architecture to enable use of a representation of the instance of the editable electronic document on both the limited-capability computing device and the high-capability computing device.
 5. The media of claim 1, wherein the network computing architecture enables the editable electronic document functionality on the high-capability computing device using script and eXtensible Markup Language HyperText Transfer Protocol (XMLHTTP) and wherein the instructions, when executed, are capable of switching between the script and XMLHTTP to a HyperText Markup Language (HTML) or Wireless Markup Language (WML) based renderable view information, the HTML or WML-based renderable view information enabling the limited-capability computing device to perform the editable electronic document functionality using full-page postback with the media.
 6. A computer-implemented method comprising: determining, based on one or more functionalities of an editable electronic document requested by a limited-capability computing device from a remote resource and based on viewing capabilities of the limited-capability computing device, that the limited-capability computing device is incapable, without external assistance, of rendering at least some view information of the editable electronic document; building, responsive to the determining and using one or more computing devices, first renderable view information that is associated with the editable electronic document and usable by the limited-capability computing device to present an item of the editable electronic document and to present indicia associated with a nested item for that item, and enabling selection of the indicia; building, responsive to receiving an indication of a selection of one of the indicia and using one or more of the one or more computing devices, a second renderable view information usable by the limited-capability computing device to present the nested item associated with the indicia effective to permit a user to navigate to the nested item, wherein one or more of the first renderable view information or the second renderable view information are configured to be utilized by the limited-capability computing device to edit an instance of the editable electronic document and to execute one or more business logic operations on the instance of the editable electronic document, the instance of the editable electronic document being stored at the remote resource, wherein the remote resource is remote from the limited-capability computing device and not on the limited-capability computing device; and editing the instance of the editable electronic document responsive to input received from the limited-capability computing device, wherein the editing comprises: receiving a postback that comprises a name-value pair; translating the postback into an event log; and editing the instance of the editable electronic document based on the event log.
 7. The method of claim 6, wherein the second renderable view information comprises a second indicia and further comprising, responsive to receiving an indication of a selection of the second indicia, building a third renderable view information usable by the limited-capability computing device to present an item subordinate to the nested item or an item superior to the nested item effective to permit the user to navigate to the subordinate or superior item.
 8. The method of claim 6, further comprising receiving hierarchical view information associated with the editable electronic document and having the item and the nested item and wherein the act of building builds the first renderable view information based on the hierarchical view information and renderable pieces of view information.
 9. The method of claim 8, wherein the hierarchical view information further comprises an item subordinate to the nested item, and wherein the method is further effective to enable a user to navigate through the hierarchical view information to navigate to the item, the nested item, and the subordinate item.
 10. The method of claim 6, wherein the indicia comprises text from a textual nested item related to said nested item or from said nested item.
 11. The method of claim 6, wherein the act of building the first renderable view information is performed without user interaction.
 12. The method of claim 6, further comprising receiving an edit to the nested item, altering the instance of the editable electronic document responsive to the edit, and enabling a higher-capability computing device to view and interact with the instance of the editable electronic document.
 13. The method of claim 6, wherein the limited-capability of the limited-capability device is a display incapable of presenting at once the nested item, its sibling nested items, and superior or subordinate items of the nested item and the superior or subordinate item's sibling nested items.
 14. A computer-implemented method comprising: receiving, using a first computing device, viewing capabilities of a second computing device or a request to treat the second computing device as not permitting two or more hierarchical viewing levels to be presented at once; building, if the viewing capabilities permit two or more of the hierarchical viewing levels to be presented at once, using the first computing device, and from hierarchical view information associated with an editable electronic document having hierarchical viewing levels, renderable view information by which the second computing device is enabled to present the two or more of the hierarchical viewing levels, or building, if the viewing capabilities do not permit two or more of the hierarchical viewing levels to be presented at once or the request is received, using the first computing device, and from the hierarchical view information associated with the editable electronic document having hierarchical viewing levels, renderable view information by: extracting textual information about items in one of the two or more hierarchical viewing levels that are presented; retrieving only a first textual nested item at a next hierarchical viewing level for presentation associated with the one of the two or more hierarchical viewing levels that are presented; and enabling the second computing device to present the one of the two or more hierarchical viewing levels with the first textual nested item from the next hierarchical viewing level; enabling, using the first computing device, an edit to an instance of the editable electronic document through the renderable view information, the renderable view information being separate from the instance of the editable electronic document; and editing, using the first computing device, the instance of the editable electronic document responsive to receiving an indication of an edit to one or more of the hierarchical viewing levels via the renderable view information to provide an edited instance of the editable electronic document, the indication of the edit to the one or more of the hierarchical viewing levels being received from the second computing device and the editing including causing one or more business logic operations to be executed via the instance of the editable electronic document, the second computing device displaying the renderable view information and being remote from a resource on which the editable electronic document is edited and stored, wherein the editing comprises: receiving the indication of the edit as a postback that comprises a name-value pair; translating the postback into an event log; and editing the instance of the editable electronic document based on the event log.
 15. The method of claim 14, further comprising building the renderable view information with indicia, selection of one or more of the indicia enabling a user to select to view another hierarchical level.
 16. The method of claim 15, further comprising building the different renderable view information responsive to a selection to view another hierarchical level and by which the second computing device is enabled to present said another hierarchical level.
 17. The method of claim 14, wherein the request is not received and the act of building is performed without user interaction.
 18. The method of claim 14, wherein the editable electronic document is an editable electronic form.
 19. The method of claim 18, further comprising, if the viewing capabilities permit two or more of the hierarchical viewing levels to be presented at once, building different renderable view information by which a different computing device with different viewing capabilities that do not permit two or more of the hierarchical viewing levels to be presented at once is enabled to continue editing the edited data instance.
 20. The method of claim 18, further comprising, if the viewing capabilities do not permit two or more of the hierarchical viewing levels to be presented at once or the request is received, building different renderable view information by which a different computing device with different viewing capabilities that permit two or more of the hierarchical viewing levels to be presented at once is enabled to continue editing the edited data instance. 